Skip to content

testing/synctest: document channel and timer violations as fatal - #80908

Open
serhiy-bzhezytskyy wants to merge 1 commit into
golang:masterfrom
serhiy-bzhezytskyy:synctest-doc-fatal
Open

testing/synctest: document channel and timer violations as fatal#80908
serhiy-bzhezytskyy wants to merge 1 commit into
golang:masterfrom
serhiy-bzhezytskyy:synctest-doc-fatal

Conversation

@serhiy-bzhezytskyy

Copy link
Copy Markdown

The difference between a panic and a fatal panic is observable: recover
cannot contain a fatal panic. A test that creates a channel inside a
bubble and sends on it after the bubble has returned aborts the
process, and a deferred recover never runs.

CL 696195 changed bubble violations for channel and timer operations
from regular panics to fatal panics, so that all bubble violations are
consistently fatal. The package doc comment still says that operating
on a bubbled channel, timer or ticker from outside the bubble panics.

The neighboring sentences in the same section were updated to say "is
a fatal error" in CL 675617, for WaitGroup.Add/Go and for Cond.Wait.
This makes the channel, timer and ticker sentence agree with them.

Updates #74837

The difference between a panic and a fatal panic is observable: recover
cannot contain a fatal panic. A test that creates a channel inside a
bubble and sends on it after the bubble has returned aborts the
process, and a deferred recover never runs.

CL 696195 changed bubble violations for channel and timer operations
from regular panics to fatal panics, so that all bubble violations are
consistently fatal. The package doc comment still says that operating
on a bubbled channel, timer or ticker from outside the bubble panics.

The neighboring sentences in the same section were updated to say "is
a fatal error" in CL 675617, for WaitGroup.Add/Go and for Cond.Wait.
This makes the channel, timer and ticker sentence agree with them.

Updates golang#74837
@gopherbot

Copy link
Copy Markdown
Contributor

This PR (HEAD: 9ef34d1) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/816240.

Important tips:

  • Don't comment on this PR. All discussion takes place in Gerrit.
  • You need a Gmail or other Google account to log in to Gerrit.
  • To change your code in response to feedback:
    • Push a new commit to the branch used by your GitHub PR.
    • A new "patch set" will then appear in Gerrit.
    • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
    • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
    • Multiple commits in the PR will be squashed by GerritBot.
  • The title and description of the GitHub PR are used to construct the final commit message.
    • Edit these as needed via the GitHub web interface (not via Gerrit or git).
    • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
  • See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants